-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
filter empty sql to avoid IndexOutOfBoundException #246
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: ⚆ Trung Nguyen <[email protected]>
@@ -102,6 +102,7 @@ public Flux<H2Result> execute() { | |||
Assert.requireTrue(!this.bindings.open, "No unfinished bindings!"); | |||
|
|||
return Flux.fromArray(this.sql.split(";")) | |||
.filter(sql -> !sql.trim().isEmpty()) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think there is a bigger problem.
split(";")
cannot be used to break SQL into separate statements properly. This character may be used in comments, various types of character string literals, and quoted identifiers.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You are right. If we remove the split, would it there be any serious implication? Mainly backward compatibility IMO.
Or we need to have a more sophisticated split than just string split.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It would be so great to be able to make use of H2's internal parsing utils instead of us having to make a dance around H2 externally. Too bad, I wasn't able to convince @katzyn to bring this project closer to H2.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we consider this fix as an interim patch while having much more careful changes to deal with ;
parsing?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I stumbled over the semicolon problem and opened an issue before I happened to have a look here and saw this discussion.
resolves #245
Make sure that: